Integrating additional information into a telecommunications call

ABSTRACT

Methods, systems, and apparatus include computer programs encoded on a computer-readable storage medium, including a method for providing information. A request is received by a call routing server to establish a call between a client device and a remote telecommunications device. A given transmission criterion that triggered distribution of the particular digital component to the client device is determined by a call context server. A set of contextual information that is mapped to the given transmission criterion is identified, by the call context server, in a data store storing a mapping of transmission criteria to contextual information. The client device is connected, by the call routing server, to the remote telecommunications device using the phone number. The set of contextual information is transmitted to the remote telecommunications device or a computing device that is associated with the remote telecommunications device while the call is being connected or in progress.

BACKGROUND

This specification relates to integrating additional information into atelecommunications call.

The Internet provides access to a wide variety of resources,information, and types of content. Some forms of content cause clientdevices to take action in response to user interaction with the content.For example, content that includes a click-to-call component causes aclient device to initiate a telephone call when a user interacts withthe click-to-call component.

SUMMARY

In general, in one aspect there is provided a method, comprising:receiving, by a call routing server, a request to establish a callbetween a client device and a remote telecommunications device, therequest including an indication that a click-to-call control wasinteracted with when visually presented at the client device, theclick-to-call control being presented together with a particular digitalcomponent; determining, by a call context server and based on a phonenumber included in the request, a given transmission criterion thattriggered distribution, to the client device, of the particular digitalcomponent that was visually presented with the click-to-call control atthe client device at a time of the interaction with the click-to-callcontrol; identifying, in a data store storing a mapping of transmissioncriteria to contextual information and by the call context server, a setof contextual information that is mapped to the given transmissioncriterion; connecting, by the call routing server, the client device tothe remote telecommunications device using the phone number; andtransmitting, by the call context server, the set of contextualinformation to the remote telecommunications device or a computingdevice that is associated with the remote telecommunications devicewhile the call is being connected or in progress.

Receiving an indication that a click-to-call control was interacted withat a client device may comprise receiving VoIP call information thatspecifies the phone number corresponding to the particular digitalcomponent that was presented with the click-to-call control; andtransmitting the set of contextual information to the remotetelecommunications device comprises embedding the set of contextualinformation in VoIP call setup data that is transmitted to the remotetelecommunications device.

Transmitting the set of contextual information to the remotetelecommunications device may comprise transmitting an audible messagethat audibly conveys the set of contextual information when the remotetelecommunications device is activated to receive the call, but prior toenabling audio communications between a user of the client device and auser of the remote telecommunications device.

Receiving a request to establish a call may comprise receiving a requestthat specifies a search query that triggered presentation of theparticular digital component that was visually presented with theclick-to-call control at the client device at a time of the interactionwith the click-to-call control; and transmitting the set of contextualinformation to the remote telecommunications device comprises generatingpacketized data that specifies a particular post call activity that ismapped to the given transmission criterion in the data store.

The packetized data may cause the remote telecommunications device tovisually present the particular post call activity on a display.

Transmitting the set of contextual information to the remotetelecommunications device may comprise transmitting the set ofcontextual information as caller identification information that ispresented in a caller identification field of a display of the remotetelecommunications device. Transmitting the set of contextualinformation to the remote telecommunications device may comprisetransmitting text to speech data specifying the set of contextualinformation to the remote telecommunications device.

Determining, by a call context server and based on the phone numberincluded in the request, a given transmission criterion that triggereddistribution, to the client device, of the particular digital componentthat was visually presented with the click-to-call control at the clientdevice at a time of the interaction with the click-to-call control maycomprise: determining the particular digital component based on thephone number included in the request, and determining, based on the timeof the interaction or an identifier of the particular digital component,the given transmission criterion.

It will be appreciated that aspects can be implemented in any convenientform. For example, aspects may be implemented by appropriate computerprograms which may be carried on appropriate carrier media which may betangible carrier media (e.g. disks) or intangible carrier media (e.g.communications signals). Aspects may also be implemented using suitableapparatus which may take the form of programmable computers runningcomputer programs arranged to implement the invention. Aspects can becombined such that features described in the context of one aspect maybe implemented in another aspect.

Particular implementations may realize none, one or more of thefollowing advantages. A recipient of a call that originates from userinteraction with a click-to-call control can be presented withadditional information (e.g., other than information provided by theclick-to-call control) obtained from user interactions with resourcesother than the click-to-call control. The additional information can beused to automatically populate data fields associated with the call,which can reduce data entry errors and complete various tasks associatedwith the call in less time. The additional information can includeonline activity (or information derived from online activity) performedat the client device (or by a user of the client device) prior to userinteraction with the click-to-call control. The online activity can beembedded into data fields of the call data created by the userinteraction with the click-to-call control to generate a combined dataset that includes both information required to connect the client deviceto the called number and the additional information. Embedding theadditional data into the combined data set enables the device thatreceives the call to obtain and/or present the additional data prior tothe call being answered, thereby providing additional information aboutthe nature or purpose of the call prior to the call being answered.Additional information that would otherwise not be available at a calleddevice is able to be presented by providing the additional information(e.g., user online activity or activity with an application installed ona calling device) by formatting the additional information as call dataand providing the information to the called device. Implementations mayaddress problems associated with how to provide information about acaller to a call recipient associated with the caller's online activity.

The details of one or more implementations of the subject matterdescribed in this specification are set forth in the accompanyingdrawings and the description below. Other features, aspects, andadvantages of the subject matter will become apparent from thedescription, the drawings, and the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of an example environment in which content isdistributed to client devices.

FIG. 2 shows an example system for providing contextual informationassociated with a call that is being connected.

FIG. 3 is a flowchart of an example process for providing contextualinformation associated with a call that is being connected.

FIG. 4 is a block diagram of an example computer system that can be usedto implement the methods, systems and processes described in thisdisclosure.

Like reference numbers and designations in the various drawings indicatelike elements.

DETAILED DESCRIPTION

Systems, methods, and computer program products are described forproviding additional information (also referred to as contextualinformation) beyond that used to connect a telecommunications call to acallee. For example, a request can be received by a call routing serverto establish a call between a client device and a remotetelecommunications device (e.g., that is located at a different locationthan the client device). The request can include an indication (e.g., adata flag or other data) that a click-to-call control was interactedwith, e.g., by a user, when visually presented at the client device. Theclick-to-call control can be presented together with a particulardigital component, such as being provided as a control presented with asearch results page presented in response to a search query that wassubmitted from the client device, e.g., by the user.

Based on a phone number included in (or received with) the request, acall context server can determine a given transmission criterion thattriggered distribution, to the client device, of the particular digitalcomponent. For example, the given transmission criterion can be a searchquery (or a phrase matching the search query, such as a distributionkeyword) that triggered presentation of the particular digital componentthat was visually presented with the click-to-call control at the clientdevice when the user interacted with the click-to-call control.

Using the given transmission criterion, the call context server canidentify a set of contextual information that is mapped to the giventransmission criterion, and transmit the set of contextual informationto the remote telecommunications device being called or a computingdevice that is associated with the remote telecommunications device,e.g., while the call is being connected or is in progress. In someimplementation, the call context server transmits the set of contextualinformation to the remote telecommunications device while the callrouting server connects the client device to the remotetelecommunications device (e.g., in parallel or asynchronously). In someimplementations, the call context server transmits the set of contextualinformation to the remote telecommunications device by way of the callrouting server. For example, the call context server can provide the setof contextual information to the call routing server, which can, inturn, include the set of contextual information in call setup data thatis transmitted to the remote telecommunications device to establish thecall or other call data that is transmitted to the remotetelecommunications device during the call setup or after the call setupis complete. When the remote telecommunications device receives the setof contextual information, the remote telecommunications device canpresent some, or all of, the set of contextual information in a displayduring call set up, or during the call.

The mapping of contextual information to transmission criterion canoccur over time, for example, using historical information identifyinguser interactions and corresponding results. For example, the historicalinformation can identify keywords used by users (such as in searchqueries), the corresponding resources that were selected based on thekeywords and presented to the users, and conversions by the users.Conversions can include, for example, user selection of click-to-callcontrols, user purchases, user navigation to or selection of othercontent, or other user actions resulting from the presentation of andreaction to content. The mapping, for example, can indicate (or be usedto infer) user interest in a topic, such as by identifying keywords thattrigger the presentation of content to the user that is related to aspecific topic.

FIG. 1 is a block diagram of an example environment 100 in which contentis distributed to client devices. The example environment 100 includes anetwork 102, such as a local area network (LAN), a wide area network(WAN), the Internet, or a combination thereof. The network 102 connectselectronic document servers 104, client devices 106, third-party contentservers 108, and a third-party content distribution system 110 (alsoreferred to as a content distribution system). The example environment100 may include many different electronic document servers 104, clientdevices 106, and third-party content servers 108. In someimplementations, content can be provided to remote telecommunicationsdevices 128, e.g., that support systems and entities providing productsand/or services. For example, the remote telecommunications devices 128can include communications devices located at entities that may provideproducts and/or services to users who use the client devices 106.Further, the environment 100 can enable communications between the usersand the entities, as described in more detail below. In someimplementations, the third-party content distribution system 110 caninclude a call routing server 214 (e.g., for routing click-to-callcalls) and a call context server 220 (e.g., for providing contextualinformation for the routed calls), as described below with reference toFIG. 2.

A client device 106 is an electronic device that is capable ofrequesting and receiving resources (e.g., electronic documents) over thenetwork 102. Example client devices 106 include personal computers,mobile communication devices, and other devices that can send andreceive data over the network 102. A client device 106 typicallyincludes a user application, such as a web browser, to facilitate thesending and receiving of data over the network 102, but nativeapplications executed by the client device 106 can also facilitate thesending and receiving of data over the network 102.

An electronic document is data that presents a set of content at aclient device 106. Examples of electronic documents include webpages,word processing documents, portable document format (PDF) documents,images, videos, search results pages, and feed sources. Nativeapplications (e.g., “apps”), such as applications installed on mobile,tablet, or desktop computing devices are also examples of electronicdocuments. Electronic documents can be provided to client devices 106 byelectronic document servers 104. For example, the electronic documentservers 104 can include servers that host publisher websites. In thisexample, the client device 106 can initiate a request for a givenpublisher webpage, and the electronic document server 104 that hosts thegiven publisher webpage can respond to the request by sending machineexecutable instructions that initiate presentation of the given webpageat the client device 106.

In another example, the electronic document servers 104 can include appservers from which client devices 106 can download apps. In thisexample, the client device 106 can download files required to install anapp at the client device 106, and then execute the downloaded applocally.

Electronic documents can include a variety of content. For example,electronic document can include static content (e.g., text or otherspecified content) that is within the electronic document itself and/ordoes not change over time. Electronic documents can also include dynamiccontent that may change over time or on a per-request basis. Forexample, a publisher of a given electronic document can maintain a datasource that is used to populate portions of the electronic document. Inthis example, the given electronic document can include a tag or scriptthat causes the client device 106 to request content from the datasource when the given electronic document is processed (e.g., renderedor executed) by a client device 106. The client device 106 integratesthe content obtained from the data source into a presentation of thegiven electronic document to create a composite electronic documentincluding the content obtained from the data source.

In some situations, a given electronic document can include athird-party tag or third-party script (e.g., portion of code) thatreferences the third-party content distribution system 110. In thesesituations, the third-party tag or third-party script is executed by theclient device 106 when the given electronic document is processed by theclient device 106. Execution of the third-party tag or third-partyscript configures the client device 106 to generate a content request112 for third-party content, which is transmitted over the network 102to the third-party content distribution system 110. For example, thethird-party tag or third-party script can enable the client device 106to generate packetized data request including a header and payload data.The content request 112 can include data such as a name (or networklocation) of a server from which the third-party content is beingrequested, a name (or network location) of the requesting device (e.g.,the client device 106), and/or information that the third-party contentdistribution system 110 can use to select third-party content providedin response to the request. The content request 112 is transmitted, bythe client device 106, over the network 102 (e.g., a telecommunicationsnetwork) to a server of the third-party content distribution system 110.

The content request 112 can include data specifying the electronicdocument and characteristics of locations at which third-party contentcan be presented. For example, data specifying a reference (e.g., URL)to an electronic document (e.g., webpage) in which the third-partycontent will be presented, available locations (e.g., third-partycontent slots) of the electronic documents that are available to presentthird-party content, sizes of the available locations, positions of theavailable locations within a presentation of the electronic document,and/or media types that are eligible for presentation in the locationscan be provided to the third-party content distribution system 110.Similarly, data specifying keywords associated with the electronicdocument (“document keywords”) or entities (e.g., people, places, orthings) that are referenced by the electronic document can also beincluded in the content request 112 (e.g., as payload data) and providedto the third-party content distribution system 110 to facilitateidentification of third-party content items that are eligible forpresentation with the electronic document.

Content requests 112 can also include data related to other information,such as information that the user has provided, geographic informationindicating a state or region from which the request was submitted, orother information that provides context for the environment in which thethird-party content will be displayed (e.g., a type of device at whichthe third-party content will be displayed, such as a mobile device ortablet device). Data specifying characteristics of the client device 106can also be provided in the content request 112, such as informationthat identifies a model of the client device 106, a configuration of theclient device 106, or a size (e.g., physical size or resolution) of anelectronic display (e.g., touchscreen or desktop monitor) on which theelectronic document is presented. Content requests 112 can betransmitted, for example, over a packetized network, and the contentrequests 112 themselves can be formatted as packetized data having aheader and payload data. The header can specify a destination of thepacket and the payload data can include any of the information discussedabove.

The third-party content distribution system 110 selects third-partycontent (e.g., information about apps) that will be presented with thegiven electronic document in response to receiving the content request112 and/or using information included in the content request 112. Insome implementations, the third-party content is selected in less than asecond to avoid errors that could be caused by delayed selection of thethird-party content. For example, delays in providing third-partycontent in response to a content request 112 can result in page loaderrors at the client device 106 or cause portions of the electronicdocument to remain unpopulated even after other portions of theelectronic document are presented at the client device 106. Also, as thedelay in providing third-party content to the client device 106increases, it is more likely that the electronic document will no longerbe presented at the client device 106 when the third-party content,thereby negatively impacting a user's experience with the electronicdocument. Further, delays in providing the third-party content canresult in a failed delivery of the third-party content, for example, ifthe electronic document is no longer presented at the client device 106when the third-party content is provided.

In some implementations, the third-party content distribution system 110is implemented in a distributed computing system that includes, forexample, a server and a set of multiple computing devices 114 that areinterconnected and identify and distribute third-party content inresponse to the content requests 112. The set of multiple computingdevices 114 operate together to identify a set of third-party contentthat are eligible to be presented in the electronic document from amonga corpus of millions of available third-party content (3PC1-x). Themillions of available third-party content can be indexed, for example,in a third-party corpus database 116. Each third-party content indexentry can reference the corresponding third-party content and/or includedistribution parameters (DP1-DPx) (e.g. selection criteria) thatcondition the distribution of the corresponding third-party content.

In some implementations, the distribution parameters (e.g., selectioncriteria) for a particular third-party content can include distributionkeywords that must be matched (e.g., by electronic documents or termsspecified in the content request 112) in order for the third-partycontent to be eligible for presentation. The distribution parameters canalso require that the content request 112 include information specifyinga particular geographic region (e.g., country or state) and/orinformation specifying that the content request 112 originated at aparticular type of client device (e.g., mobile device or tablet device)in order for the third-party content to be eligible for presentation.The distribution parameters can also specify a selection value (e.g.,bid) and/or budget for distributing the particular third-party content.

The identification of the eligible third-party content can be segmentedinto multiple tasks 117 a-117 c that are then assigned among computingdevices within the set of multiple computing devices 114. For example,different computing devices in the set of multiple computing devices 114can each analyze a different portion of the third-party corpus database116 to identify various third-party content having distributionparameters that match information included in the content request 112.In some implementations, each given computing device in the set ofmultiple computing devices 114 can analyze a different data dimension(or set of dimensions) and pass results 118 a-118 c of the analysis backto the third-party content distribution system 110. For example, theresults 118 a-118 c provided by each of the computing devices in the setmay identify a subset of third-party content that are eligible fordistribution in response to the request and/or a subset of thethird-party content that have certain distribution parameters orattributes.

In some implementations, a contextual database 124, e.g., maintained bythe third-party content distribution system 110, can store contextualinformation that includes (and identifies relationships among) contentrequests 112 (e.g., search queries) and corresponding reply data 120(e.g., search results). The contextual information can also includethird-party requests 121 and resulting third-party data 122. In someimplementations, the contextual database 124 can maintain historicalcontextual information, e.g., based on past user interactions, and/orcontextual information for a current session, such as a current contentrequest 112, current reply data 120, a current third-party request 121,and/or current third-party data 122.

The third-party content distribution system 110 aggregates the results118 a-118 c received from the set of multiple computing devices 114 anduses information associated with the aggregated results to select one ormore instances of third-party content that will be provided in responseto the content request 112. For example, the third-party contentdistribution system 110 can select a set of winning third-party contentbased on the outcome of one or more content evaluation processes. Inturn, the third-party content distribution system 110 can generate andtransmit, over the network 102, reply data 120 (e.g., digital datarepresenting a reply) that enable the client device 106 to integrate theset of winning third-party content into the given electronic document,such that the set of winning third-party content and the content of theelectronic document are presented together at a display of the clientdevice 106.

In some implementations, the client device 106 executes instructionsincluded in the reply data 120, which configures and enables the clientdevice 106 to obtain the set of winning third-party content from one ormore third-party content servers. For example, the instructions in thereply data 120 can include a network location (e.g., a Uniform ResourceLocator (URL)) and a script that causes the client device 106 totransmit a third-party request 121 to the third-party content server 108to obtain a given winning third-party content from the third-partycontent server 108. In response to the request, the third-party contentserver 108 will transmit, to the client device 106, third-party data 122that causes the given winning third-party content to be incorporatedinto the electronic document and presented at the client device 106.

In some implementations, a click-to-call request 126 that is presentedat the client device 106 can be used to access content. For example, thereply data 120 or the third-party data 122 can be formatted at requesttime to include the click-to-call request 126, e.g., in response to thecontent request 112 or the third-party request 121, respectively. As aresult, the click-to-call request 126 can include a script that dials aparticular phone number in response to user interaction with theclick-to-call control and also initiates a request for additional datathat will be appended to the call. For example, the particular phonenumber can be a phone number that connects a user of the client device106 to a callee identified in the reply data 120 or third-party data122. Meanwhile, the additional data requested in response to the userinteraction with the click-to-call control can include contextualinformation that is obtainable from the contextual database 124. Thecontextual information can be presented, for example, to the callee atthe remote telecommunications device 128 so that the callee can obtainsome context as to the nature of the call prior to answering the call.Further details regarding the use of the click-to-call request 126 andresulting operations are described below with reference to FIGS. 2 and3.

FIG. 2 shows an example system 200 for providing contextual informationassociated with a call that is being connected. For example, a user 206using a client device 106 a can select a click-to-call control 210presented with a digital component 212, e.g., a search results page, awebpage, a landing page, or some other resource. The click-to-callcontrol 210 can be presented with a content item being presented to theuser in the digital component 212, such as published by an entity thatis called in response to the user interaction with the click-to-callcontrol 210. In some implementations, stages 1-5 can be used forhandling a click-to-call request 216 that is initiated upon userinteraction with the click-to-call control 210.

In some implementations, a digital component is a discrete unit ofcontent that is inserted into an electronic document that includes otherinformation. For example, the digital component can be one or more filesthat present text, images, and/or other content within a web page orother resource, and can in some embodiments be formatted as anadvertisement (or convey advertising information). In theseimplementations, the digital component can be provided from a differentsource (e.g., a digital component server) than the electronic document(e.g., web page or native application) in which the digital component ispresented. As such, the digital component can be integrated into theelectronic document when the electronic document is rendered at a clientdevice.

At stage 1, as a result of the selection of the click-to-call control210, the click-to-call request 216 can be received at a call routingserver 214 for establishing a call 202 between the client device 106 aand the remote telecommunications device 128. The click-to-call request216 can indicate, for example, that the click-to-call control 210 wasinteracted with by the user 206 on the digital component 212 (e.g., adigital component maintained by an entity that is called in response touser interaction with the click-to-call control or a portion of contentpresented with the digital component).

At stage 2, using information in the click-to-call request 216, a callcontext server 220 can determine a given transmission criterion 222 athat triggered distribution of the digital component 212 that wasvisually presented with the click-to-call control was interacted with atthe client device 106 a. For example, assume that the digital component212 is presented in a search results page at the client device 106 a. Inthis example, the given transmission criterion 222 a may include thesearch query that was used to trigger presentation of the search resultspage and/or the digital component 212.

At stage 3, the call context server 220 can use the given transmissioncriterion 222 a to identify a set of contextual information 226. Forexample, the call context server 220 can use a data store 228 thatidentifies relationships between transmission criteria 230 andcontextual information 232 to identify (e.g., lookup) the contextualinformation. As a result, the set of contextual information 226 that isidentified can provide information as to what the user 206 might becalling about in order to provide the information to the callee 208 sothat, for example, the callee 208 can better assist the caller.

At stage 4, the call routing server 214 can connect the call 202 betweenthe client device 106 a (e.g., a mobile device of the user 206) with theremote telecommunications device 128 (e.g., a computer at the callee'slocation 204). The connection can be made, for example, using a phonenumber 224 identified in the click-to-call request 216.

At stage 5, the call context server 220 can transmit the set ofcontextual information (e.g., “user X is calling for reason Y”) to theremote telecommunications device 128. The contextual information can becommunicated to the callee in a variety of ways prior to the calleebeing placed in communication with the caller. For example, thecontextual information can be provided in a form of a “whisper” thataccompanies the incoming call, such as in a message audibly presented tothe callee 208 prior to communication between the caller and callee 208.In some implementations, the contextual information is presented invisual form, such as in a caller identification field 234 in a display236 that is displayed on the remote telecommunications device 128.Alternatively, or additionally, the contextual information can betransmitted to a computing device (or mobile device) of the callee. Forexample, the contextual information could be sent as a text message,multimedia message, e-mail, instant message, or in another form, andpresented by a device other than the remote telecommunications device128 that receives the phone call. As such, the contextual informationcan be provided even when the callee's phone does not supportpresentation of the contextual information.

FIG. 3 is a flowchart of an example process 300 for providing contextualinformation associated with a call that is being connected. In someimplementations, the third-party content distribution system 110 andcomponents that it includes can perform steps of the process 300 usingone or more servers and a memory device storing instructions that areexecuted by one or more processors. For example, the call routing server214 can route calls resulting from the selection of click-to-callcontrols, and the call context server 220 can provide contextualinformation for the calls. FIGS. 1 and 2 are used to provide examplestructures for performing the steps of the process 300. For example,stages 1-5 described with reference to FIG. 2 track to steps 302-310,respectively.

The process 300 can begin, for example, when a request is received by acall routing server to establish a call between a client device and aremote telecommunications device (302). The request includes anindication that a click-to-call control was interacted with whenvisually presented at the client device, the click-to-call control beingpresented together with a particular digital component. For example, thecall routing server 214 can receive (e.g., at stage 1 in FIG. 2) theclick-to-call request 216 to establish the call 202 between the clientdevice 106 a and the remote telecommunications device 128. Theclick-to-call request 216 can indicate (e.g., using an indication 218)that the click-to-call control 210 was selected by the user 206 on thedigital component 212 (e.g., an advertisement or a webpage provided byan entity that is called in response to user interaction with theclick-to-call control).

In some implementations, the click-to-call request 216 can includeinformation about a user initiating the request, such as informationobtained from a cookie associated with the user 206 and stored on theclient device 106 a. In some implementations, cookie information in thecookie can include information about the user 206 and information aboutpast interactions of the user 206. For example, the cookie informationcan include information identifying previous online search activity,browsing history, transaction history, or other online activity.

A given transmission criterion that triggered distribution of theparticular digital component to the client device is determined (304).The given transmission criterion can be the transmission criterion thatcaused the particular digital component to be visually presented withthe click-to-call control at the time of the user interaction with theclick-to-call control. The given transmission criterion that triggereddistribution of the particular digital component can be determined basedon a phone number that is included in the request. For example, usinginformation in the click-to-call request 216, the call context server220 can determine (e.g., at stage 2 in FIG. 2) that the giventransmission criterion 222 a is a search query entered by the user 206on the client device 106 a. Identifying the search query as the giventransmission criterion 222 a can include, for example, identifyingsearch query terms that are included in the search query that resultedin the presentation of the digital component 212 (e.g., the callee'sentity's digital component). The search query terms can include, forexample, search query terms that identify an entity of the callee 208.For example, the search query terms can identify the entity by name, orthe search query terms can identify a product or service that is offeredby the entity. The phone number 224 included in the click-to-callrequest 216 can be a phone number, for example, that is known to be tiedto the callee 208. The phone number 224 can also be used, together withthe search query terms, to identify the transmission criterion. The callcontext server 220 can make the determination, for example, by lookingup transmission criteria associated with the phone number 224 (e.g.,555-111-xxxx) that is included in the click-to-call request 216 and thatmatches the phone number presented with the click-to-call control 210.The call context server 220 can further identify the phone number 224,for example, as a phone number belonging to the callee's location 204,and use that information along with other information in theclick-to-call request 216 to identify the given transmission criterion222 a. Other ways for identifying the given transmission criterion canbe used, such as by using information from the contextual database 124that indicates past user interactions with content or interactions bythe user in a current session. For example, the contextual informationcan include terms from search queries submitted by the user or termsfrom search results pages (of subsequent pages) that resulted from thesearch queries.

In some implementations, interactions by the user in a current sessionor at a previous time can be identified from information in a cookie,such as identifying the name of the entity tied to the particulardigital component and optionally including information identifying pastuser interactions with the particular digital component. Information inthe cookie, such as an identifier or other information of the user 206,can be included in the click-to-call request 216 and used to map theclick-to-call request 216 to the user 206.

In some implementations, determining the given transmission criterionthat triggered distribution, to the client device, of the particulardigital component includes determining the particular digital componentbased on the phone number included in the request and determining, basedon the time of the interaction or an identifier of the particulardigital component, the given transmission criterion. For example, bycomparing times of the presentation of the digital component andselection of the click-to-call control 210, the call context server 220can determine that the given transmission criterion resulted in thepresentation of the digital component 212. A comparison can be made, forexample, between a time that a search query was entered and a time thatthe click-to-call request 216 was made from a digital component providedto the user 206 in response to, or as a result of, the search query. Ifa difference in the times is below a threshold (e.g., five minutes),then the search query can be determined to be the given transmissioncriterion 222 a. In another example, the call context server 220 candetermine the given transmission criterion 222 a based on an identifierof the digital component 212. For example, if the digital component 212is a webpage owned or published by the callee 208, then identifying thegiven transmission criterion 222 a can include parsing a URL or otherindicator of the digital component or parsing the digital componentitself. The parsing can extract terms that identify, for example, thename of the callee 208 or an entity owned or operated by the callee 208,the entity providing products and/or services of the callee 208. In someimplementations, the time of the interaction can correspond to atime-of-day that indicates a likelihood that the caller has a particularinterest or is likely to take a particular action. For example,historical information may show that late afternoon selection by usersof click-to-call controls have a high correlation with products andservices received the next day.

A set of contextual information that is mapped to the given transmissioncriterion is identified, by the call context server, in a data storestoring a mapping of transmission criteria to contextual information(306). For example, the call context server 220 can use the giventransmission criterion 222 a to identify (e.g., at stage 2 in FIG. 2)the set of contextual information 226. The call context server 220 canuse the data store 228 that identifies, for example, relationshipsbetween transmission criteria 230 and contextual information 232. Forexample, the data store 228 can include an entry 228 a that, when thetransmission criteria 230 includes certain search query terms, thecontextual information 232 specifies that user X is calling for reasonY.

In some implementations, historical data identifying past or recentinteractions of the user 206 can be used to determine content. Forexample, prior to selecting the click-to-call control 210, if the user206 has searched for subject Z (or viewed digital components containinginformation about subject Z), the click-to-call request 216 can includeinformation identifying subject Z. A mapping can be created, forexample, between contextual data and a search history of the user 206.In some implementations, more recent search activity of the user 206 canindicate a greater confidence, for example, of the mapping than say asearch activity that is several days old.

The client device is connected, by the call routing server, to theremote telecommunications device using the phone number (308). Forexample, the call routing server 214 (e.g., at stage 4 in FIG. 2) canconnect the client device 106 a (e.g., a mobile device of the user 206)with the remote telecommunications device 128 (e.g., a telephone orcomputer at the callee's location 204). The connection can be made, forexample, using the phone number 224 identified in the click-to-callrequest 216.

The set of contextual information is transmitted, by the call contextserver, to the remote telecommunications device or a computing devicethat is associated with the remote telecommunications device while thecall is being connected or in progress (310). For example, the callcontext server 220 can transmit (e.g., at stage 5 in FIG. 2) the set ofcontextual information (e.g., “user X is calling for reason Y”) to theremote telecommunications device 128. In some implementations, thecontextual information can be in a form of a whisper that accompaniesthe incoming call, such as in a message that can be heard by the callee208 that is listened to before communicating with the caller. In someimplementations, the contextual information is presented in visual form,such as in a caller identification field 234 in a display 236 that isdisplayed on the remote telecommunications device 128.

In some implementations, the indication that a click-to-call control wasinteracted with at a client device is received in the form of Voice overInternet Protocol (VoIP) call information that specifies the phonenumber corresponding to the particular digital component that waspresented with the click-to-call control. In these situations, the setof contextual information that is transmitted to the remotetelecommunications device can be embedded in VoIP call setup data thatis transmitted to the remote phone device. For example, the call contextserver 220 can format text included in the set of contextual information226 into digital data that can be inserted into a field of the VoIP callsetup data. In this way, the context of the call 202 can be reproducedat the remote telecommunications device 128, for example, as textpresented in a display of the called telecommunications device. In someimplementations, VoIP call setup techniques can be used to createpackets that include other multimedia features, including videocapabilities, such as to graphically provide a caller's reason for thecall in the caller identification field 234 or to connect the call 202as an audio-visual presentation. For example, techniques for handlingVoIP calls can include signaling, channel set-up, digitization of analogvoice signals (or translation from text), encoding, and thentransmission of IP packets over a packet-switched network. In this way,the call 202 and the contextual information 226 can be delivered to thecallee 208 who may be using a combination of headsets, computer screens,and/or other equipment.

In some implementations, the set of contextual information istransmitted to the remote telecommunications device in the form of anaudible message that audibly conveys the set of contextual informationwhen the remote telecommunications device is activated to receive thecall, but prior to enabling audio communications between a user of theclient device and a user of the remote telecommunications device. Forexample, the set of contextual information 226 can be provided as awhisper that can be listened to by the callee 208 before starting aconversation with the user 206.

In some implementations, the request to establish the call specifies asearch query that triggered presentation of the particular digitalcomponent that was visually presented with the click-to-call control atthe client device at a time of the interaction with the click-to-callcontrol. In these situations, packetized data that specifies aparticular post call activity that is mapped to the given transmissioncriterion in the data store can be generated and transmitted to theremote telecommunications device. For example, based on information inthe received click-to-call request 216, the call context server 220 candetermine that a search query (e.g., “nearby Z entities”) entered by theuser 206 on the client device 106 a is the transmission criterion 222 bthat resulted in presentation of the digital component 212 (e.g., asearch result or advertisement related to Z entities). As a result, theset of contextual information 226 provided by the call routing server214 to the remote telecommunications device 128 can indicate that user Xis calling for reason Y, as determined by a mapping by the entry 228 ain the data store 228.

In some implementations, the call context server 220 can use keywordsfrom the search query to determine an intent of the query and thusdetermine the set of contextual information 226. The keywords can berelated, for example, to a known set of services made available by anentity (e.g., the callee's location 204). In some implementations, thecall context server 220 can determine the set of contextual information226 from keywords that appear on a digital component (e.g., thatcontains the click-to-call control 210) arrived at by the user from thesearch results of the query.

In some implementations, the packetized data can cause the remotetelecommunications device to visually present the particular post callactivity on a display. For example, the set of contextual information226 can include information about the call 202 in the display 236 on theremote telecommunications device 128. The post call activity caninclude, for example, information received from the client device 106 athat can be used to display initial information in a visualrepresentation of a conversation between the user 206 and the callee208.

In some implementations, the set of contextual information istransmitted as caller identification information that is presented in acaller identification field of a display of the remotetelecommunications device. For example, the caller identification field234 in the display 236 presented on the remote telecommunications device128 can identify reason Y as the post call activity associated with thecall 202 being received by the callee 208.

In some implementations, transmitting the set of contextual informationto the remote telecommunications device can include transmitting text tospeech data specifying the set of contextual information to the remotetelecommunications device. For example, information provided by the callcontext server 220 for use in the caller identification field 234 caninclude information generated from the contextual information 232. Thedigital data can be consumed by the remote telecommunications device128, such as to produce a whisper that precedes an audible connectionbetween the user 206 and the callee 208.

In some implementations, the set of contextual information 226 caninclude information, such as user-specific information, that can be usedat the remote telecommunications device 128 to automatically performfunctions. For example, applications executing at the remotetelecommunications device 128 can automatically fill in user-relatedinformation, such as in forms, or automatically navigate to screensassociated with certain types of users or services, to name a fewexamples. In some implementations, the set of contextual information 226can include information by which scheduling can occur, e.g., to displayavailable time slots for providing a service related to the contextualinformation associated with the user making the call 202. In someimplementations, the set of contextual information 226 (or the call-fromnumber) can be used to automatically look up user information, such asfrom a user file, at the time that the call 202 is being connected,thereby streamlining interaction with the caller during the call.

In some implementations, the set of contextual information 226 can bedetermined and passed in various ways. For example, in a mobile context,the tapping of a phone number link can be tracked, and details about thecaller can be passed to a business (e.g., the callee's location 204). Insome implementations, an intermediary server, such as the call routingserver 214, can serve as an intermediary server that call-forwards aunique phone number that is presented to the user 206 with theclick-to-call control 210. In this example, the call routing server 214can provide query information used by the user 206, e.g., includingquery terms resulted in search results leading to presentation of theclick-to-call control 210.

FIG. 4 is a block diagram of example computing devices 400, 450 that maybe used to implement the systems and methods described in this document,as either a client or as a server or plurality of servers. Computingdevice 400 is intended to represent various forms of digital computers,such as laptops, desktops, workstations, personal digital assistants,servers, blade servers, mainframes, and other appropriate computers.Computing device 400 is further intended to represent any othertypically non-mobile devices, such as televisions or other electronicdevices with one or more processers embedded therein or attachedthereto. Computing device 450 is intended to represent various forms ofmobile devices, such as personal digital assistants, cellulartelephones, smartphones, and other computing devices. The componentsshown here, their connections and relationships, and their functions,are meant to be examples only, and are not meant to limitimplementations of the inventions described and/or claimed in thisdocument.

Computing device 400 includes a processor 402, memory 404, a storagedevice 406, a high-speed controller 408 connecting to memory 404 andhigh-speed expansion ports 410, and a low-speed controller 412connecting to low-speed bus 414 and storage device 406. Each of thecomponents 402, 404, 406, 408, 410, and 412, are interconnected usingvarious busses, and may be mounted on a common motherboard or in othermanners as appropriate. The processor 402 can process instructions forexecution within the computing device 400, including instructions storedin the memory 404 or on the storage device 406 to display graphicalinformation for a GUI on an external input/output device, such asdisplay 416 coupled to high-speed controller 408. In otherimplementations, multiple processors and/or multiple buses may be used,as appropriate, along with multiple memories and types of memory. Also,multiple computing devices 400 may be connected, with each deviceproviding portions of the necessary operations (e.g., as a server bank,a group of blade servers, or a multi-processor system).

The memory 404 stores information within the computing device 400. Inone implementation, the memory 404 is a computer-readable medium. In oneimplementation, the memory 404 is a volatile memory unit or units. Inanother implementation, the memory 404 is a non-volatile memory unit orunits.

The storage device 406 is capable of providing mass storage for thecomputing device 400. In one implementation, the storage device 406 is acomputer-readable medium. In various different implementations, thestorage device 406 may be a floppy disk device, a hard disk device, anoptical disk device, or a tape device, a flash memory or other similarsolid state memory device, or an array of devices, including devices ina storage area network or other configurations. In one implementation, acomputer program product is tangibly embodied in an information carrier.The computer program product contains instructions that, when executed,perform one or more methods, such as those described above. Theinformation carrier is a computer- or machine-readable medium, such asthe memory 404, the storage device 406, or memory on processor 402.

The high-speed controller 408 manages bandwidth-intensive operations forthe computing device 400, while the low-speed controller 412 manageslower bandwidth-intensive operations. Such allocation of duties is anexample only. In one implementation, the high-speed controller 408 iscoupled to memory 404, display 416 (e.g., through a graphics processoror accelerator), and to high-speed expansion ports 410, which may acceptvarious expansion cards (not shown). In the implementation, low-speedcontroller 412 is coupled to storage device 406 and low-speed bus 414.The low-speed bus 414 (e.g., a low-speed expansion port), which mayinclude various communication ports (e.g., USB, Bluetooth®, Ethernet,wireless Ethernet), may be coupled to one or more input/output devices,such as a keyboard, a pointing device, a scanner, or a networking devicesuch as a switch or router, e.g., through a network adapter.

The computing device 400 may be implemented in a number of differentforms, as shown in the figure. For example, it may be implemented as astandard server 420, or multiple times in a group of such servers. Itmay also be implemented as part of a rack server system 424. Inaddition, it may be implemented in a personal computer such as a laptopcomputer 422. Alternatively, components from computing device 400 may becombined with other components in a mobile device (not shown), such ascomputing device 450. Each of such devices may contain one or more ofcomputing devices 400, 450, and an entire system may be made up ofmultiple computing devices 400, 450 communicating with each other.

Computing device 450 includes a processor 452, memory 464, aninput/output device such as a display 454, a communication interface466, and a transceiver 468, among other components. The computing device450 may also be provided with a storage device, such as a micro-drive orother device, to provide additional storage. Each of the components 450,452, 464, 454, 466, and 468, are interconnected using various buses, andseveral of the components may be mounted on a common motherboard or inother manners as appropriate.

The processor 452 can process instructions for execution within thecomputing device 450, including instructions stored in the memory 464.The processor may also include separate analog and digital processors.The processor may provide, for example, for coordination of the othercomponents of the computing device 450, such as control of userinterfaces, applications run by computing device 450, and wirelesscommunication by computing device 450.

Processor 452 may communicate with a user through control interface 458and display interface 456 coupled to a display 454. The display 454 maybe, for example, a TFT LCD display or an OLED display, or otherappropriate display technology. The display interface 456 may compriseappropriate circuitry for driving the display 454 to present graphicaland other information to a user. The control interface 458 may receivecommands from a user and convert them for submission to the processor452. In addition, an external interface 462 may be provided incommunication with processor 452, so as to enable near areacommunication of computing device 450 with other devices. Externalinterface 462 may provide, for example, for wired communication (e.g.,via a docking procedure) or for wireless communication (e.g., viaBluetooth® or other such technologies).

The memory 464 stores information within the computing device 450. Inone implementation, the memory 464 is a computer-readable medium. In oneimplementation, the memory 464 is a volatile memory unit or units. Inanother implementation, the memory 464 is a non-volatile memory unit orunits. Expansion memory 474 may also be provided and connected tocomputing device 450 through expansion interface 472, which may include,for example, a subscriber identification module (SIM) card interface.Such expansion memory 474 may provide extra storage space for computingdevice 450, or may also store applications or other information forcomputing device 450. Specifically, expansion memory 474 may includeinstructions to carry out or supplement the processes described above,and may include secure information also. Thus, for example, expansionmemory 474 may be provided as a security module for computing device450, and may be programmed with instructions that permit secure use ofcomputing device 450. In addition, secure applications may be providedvia the SIM cards, along with additional information, such as placingidentifying information on the SIM card in a non-hackable manner.

The memory may include for example, flash memory and/or MRAM memory, asdiscussed below. In one implementation, a computer program product istangibly embodied in an information carrier. The computer programproduct contains instructions that, when executed, perform one or moremethods, such as those described above. The information carrier is acomputer- or machine-readable medium, such as the memory 464, expansionmemory 474, or memory on processor 452.

Computing device 450 may communicate wirelessly through communicationinterface 466, which may include digital signal processing circuitrywhere necessary. Communication interface 466 may provide forcommunications under various modes or protocols, such as GSM voicecalls, SMS, EMS, or MMS messaging, CDMA, TDMA, PDC, WCDMA, CDMA2000, orGPRS, among others. Such communication may occur, for example, throughtransceiver 468 (e.g., a radio-frequency transceiver). In addition,short-range communication may occur, such as using a Bluetooth®, WiFi,or other such transceiver (not shown). In addition, GPS receiver module470 may provide additional wireless data to computing device 450, whichmay be used as appropriate by applications running on computing device450.

Computing device 450 may also communicate audibly using audio codec 460,which may receive spoken information from a user and convert it tousable digital information. Audio codec 460 may likewise generateaudible sound for a user, such as through a speaker, e.g., in a handsetof computing device 450. Such sound may include sound from voicetelephone calls, may include recorded sound (e.g., voice messages, musicfiles, etc.) and may also include sound generated by applicationsoperating on computing device 450.

The computing device 450 may be implemented in a number of differentforms, as shown in the figure. For example, it may be implemented as acellular telephone 480. It may also be implemented as part of asmartphone 482, personal digital assistant, or other mobile device.

Various implementations of the systems and techniques described here canbe realized in digital electronic circuitry, integrated circuitry,specially designed ASICs (application specific integrated circuits),computer hardware, firmware, software, and/or combinations thereof.These various implementations can include implementation in one or morecomputer programs that are executable and/or interpretable on aprogrammable system including at least one programmable processor, whichmay be special or general purpose, coupled to receive data andinstructions from, and to transmit data and instructions to, a storagesystem, at least one input device, and at least one output device.

These computer programs (also known as programs, software, softwareapplications or code) include machine instructions for a programmableprocessor, and can be implemented in a high-level procedural and/orobject-oriented programming language, and/or in assembly/machinelanguage. Other programming paradigms can be used, e.g., functionalprogramming, logical programming, or other programming. As used herein,the terms “machine-readable medium” “computer-readable medium” refers toany computer program product, apparatus and/or device (e.g., magneticdiscs, optical disks, memory, Programmable Logic Devices (PLDs)) used toprovide machine instructions and/or data to a programmable processor,including a machine-readable medium that receives machine instructionsas a machine-readable signal. The term “machine-readable signal” refersto any signal used to provide machine instructions and/or data to aprogrammable processor.

To provide for interaction with a user, the systems and techniquesdescribed here can be implemented on a computer having a display device(e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor)for displaying information to the user and a keyboard and a pointingdevice (e.g., a mouse or a trackball) by which the user can provideinput to the computer. Other kinds of devices can be used to provide forinteraction with a user as well; for example, feedback provided to theuser can be any form of sensory feedback (e.g., visual feedback,auditory feedback, or tactile feedback); and input from the user can bereceived in any form, including acoustic, speech, or tactile input.

The systems and techniques described here can be implemented in acomputing system that includes a back end component (e.g., as a dataserver), or that includes a middleware component (e.g., an applicationserver), or that includes a front end component (e.g., a client computerhaving a graphical user interface or a Web browser through which a usercan interact with an implementation of the systems and techniquesdescribed here), or any combination of such back end, middleware, orfront end components. The components of the system can be interconnectedby any form or medium of digital data communication (e.g., acommunication network). Examples of communication networks include alocal area network (“LAN”), a wide area network (“WAN”), and theInternet.

The computing system can include clients and servers. A client andserver are generally remote from each other and typically interactthrough a communication network. The relationship of client and serverarises by virtue of computer programs running on the respectivecomputers and having a client-server relationship to each other.

While this specification contains many specific implementation details,these should not be construed as limitations on the scope of anyinventions or of what may be claimed, but rather as descriptions offeatures specific to particular implementations of particularinventions. Certain features that are described in this specification inthe context of separate implementations can also be implemented incombination in a single implementation. Conversely, various featuresthat are described in the context of a single implementation can also beimplemented in multiple implementations separately or in any suitablesubcombination. Moreover, although features may be described above asacting in certain combinations and even initially claimed as such, oneor more features from a claimed combination can in some cases be excisedfrom the combination, and the claimed combination may be directed to asubcombination or variation of a subcombination.

Similarly, while operations are depicted in the drawings in a particularorder, this should not be understood as requiring that such operationsbe performed in the particular order shown or in sequential order, orthat all illustrated operations be performed, to achieve desirableresults. In certain circumstances, multitasking and parallel processingmay be advantageous. Moreover, the separation of various systemcomponents in the implementations described above should not beunderstood as requiring such separation in all implementations, and itshould be understood that the described program components and systemscan generally be integrated together in a single software product orpackaged into multiple software products.

Thus, particular implementations of the subject matter have beendescribed. Other implementations are within the scope of the followingclaims. In some cases, the actions recited in the claims can beperformed in a different order and still achieve desirable results. Inaddition, the processes depicted in the accompanying figures do notnecessarily require the particular order shown, or sequential order, toachieve desirable results. In certain implementations, multitasking andparallel processing may be advantageous.

1-10. (canceled)
 11. A method, comprising: receiving, by a call routingserver, a request to establish a call between a client device and aremote telecommunications device, the request including an indicationthat a click-to-call control was interacted with when visually presentedat the client device, the click-to-call control being presented togetherwith a particular digital component; determining, by a call contextserver and based on a phone number included in the request, a giventransmission criterion that triggered distribution, to the clientdevice, of the particular digital component that was visually presentedwith the click-to-call control at the client device at a time of theinteraction with the click-to-call control; identifying, in a data storestoring a mapping of transmission criteria to contextual information andby the call context server, a set of contextual information that ismapped to the given transmission criterion; connecting, by the callrouting server, the client device to the remote telecommunicationsdevice using the phone number; and transmitting, by the call contextserver, the set of contextual information to the remotetelecommunications device or a computing device that is associated withthe remote telecommunications device while the call is being connectedor in progress.
 12. The method of claim 11, wherein: receiving anindication that a click-to-call control was interacted with at a clientdevice comprises receiving VoIP call information that specifies thephone number corresponding to the particular digital component that waspresented with the click-to-call control; and transmitting the set ofcontextual information to the remote telecommunications device comprisesembedding the set of contextual information in VoIP call setup data thatis transmitted to the remote telecommunications device.
 13. The methodof claim 11, wherein transmitting the set of contextual information tothe remote telecommunications device comprises transmitting an audiblemessage that audibly conveys the set of contextual information when theremote telecommunications device is activated to receive the call, butprior to enabling audio communications between a user of the clientdevice and a user of the remote telecommunications device.
 14. Themethod of claim 11, wherein: receiving a request to establish a callcomprises receiving a request that specifies a search query thattriggered presentation of the particular digital component that wasvisually presented with the click-to-call control at the client deviceat a time of the interaction with the click-to-call control; andtransmitting the set of contextual information to the remotetelecommunications device comprises generating packetized data thatspecifies a particular post call activity that is mapped to the giventransmission criterion in the data store.
 15. The method of claim 14,wherein the packetized data causes the remote telecommunications deviceto visually present the particular post call activity on a display. 16.The method of claim 11, wherein transmitting the set of contextualinformation to the remote telecommunications device comprisestransmitting the set of contextual information as caller identificationinformation that is presented in a caller identification field of adisplay of the remote telecommunications device.
 17. The method of claim11, wherein transmitting the set of contextual information to the remotetelecommunications device comprises transmitting text to speech dataspecifying the set of contextual information to the remotetelecommunications device.
 18. The method of claim 11, whereindetermining, by a call context server and based on the phone numberincluded in the request, a given transmission criterion that triggereddistribution, to the client device, of the particular digital componentthat was visually presented with the click-to-call control at the clientdevice at a time of the interaction with the click-to-call controlcomprises: determining the particular digital component based on thephone number included in the request, and determining, based on the timeof the interaction or an identifier of the particular digital component,the given transmission criterion.
 19. A non-transitory computer programproduct embodied in a non-transitive computer-readable medium includinginstructions, that when executed, cause one or more processors toperform operations including: receiving, by a call routing server, arequest to establish a call between a client device and a remotetelecommunications device, the request including an indication that aclick-to-call control was interacted with when visually presented at theclient device, the click-to-call control being presented together with aparticular digital component; determining, by a call context server andbased on a phone number included in the request, a given transmissioncriterion that triggered distribution, to the client device, of theparticular digital component that was visually presented with theclick-to-call control at the client device at a time of the interactionwith the click-to-call control; identifying, in a data store storing amapping of transmission criteria to contextual information and by thecall context server, a set of contextual information that is mapped tothe given transmission criterion; connecting, by the call routingserver, the client device to the remote telecommunications device usingthe phone number; and transmitting, by the call context server, the setof contextual information to the remote telecommunications device or acomputing device that is associated with the remote telecommunicationsdevice while the call is being connected or in progress.
 20. Thenon-transitory computer program product of claim 19, wherein: receivingan indication that a click-to-call control was interacted with at aclient device comprises receiving VoIP call information that specifiesthe phone number corresponding to the particular digital component thatwas presented with the click-to-call control; and transmitting the setof contextual information to the remote telecommunications devicecomprises embedding the set of contextual information in VoIP call setupdata that is transmitted to the remote telecommunications device. 21.The non-transitory computer program product of claim 19, whereintransmitting the set of contextual information to the remotetelecommunications device comprises transmitting an audible message thataudibly conveys the set of contextual information when the remotetelecommunications device is activated to receive the call, but prior toenabling audio communications between a user of the client device and auser of the remote telecommunications device.
 22. The non-transitorycomputer program product of claim 19, wherein: receiving a request toestablish a call comprises receiving a request that specifies a searchquery that triggered presentation of the particular digital componentthat was visually presented with the click-to-call control at the clientdevice at a time of the interaction with the click-to-call control; andtransmitting the set of contextual information to the remotetelecommunications device comprises generating packetized data thatspecifies a particular post call activity that is mapped to the giventransmission criterion in the data store.
 23. The non-transitorycomputer program product of claim 22, wherein the packetized data causesthe remote telecommunications device to visually present the particularpost call activity on a display.
 24. The non-transitory computer programproduct of claim 19, wherein transmitting the set of contextualinformation to the remote telecommunications device comprisestransmitting the set of contextual information as caller identificationinformation that is presented in a caller identification field of adisplay of the remote telecommunications device.
 25. The non-transitorycomputer program product of claim 19, wherein transmitting the set ofcontextual information to the remote telecommunications device comprisestransmitting text to speech data specifying the set of contextualinformation to the remote telecommunications device.
 26. Thenon-transitory computer program product of claim 19, whereindetermining, by a call context server and based on the phone numberincluded in the request, a given transmission criterion that triggereddistribution, to the client device, of the particular digital componentthat was visually presented with the click-to-call control at the clientdevice at a time of the interaction with the click-to-call controlcomprises: determining the particular digital component based on thephone number included in the request, and determining, based on the timeof the interaction or an identifier of the particular digital component,the given transmission criterion.
 27. A system comprising: one or moreprocessors; and one or more memory elements including instructions that,when executed, cause the one or more processors to perform operationsincluding: receiving, by a call routing server, a request to establish acall between a client device and a remote telecommunications device, therequest including an indication that a click-to-call control wasinteracted with when visually presented at the client device, theclick-to-call control being presented together with a particular digitalcomponent; determining, by a call context server and based on a phonenumber included in the request, a given transmission criterion thattriggered distribution, to the client device, of the particular digitalcomponent that was visually presented with the click-to-call control atthe client device at a time of the interaction with the click-to-callcontrol; identifying, in a data store storing a mapping of transmissioncriteria to contextual information and by the call context server, a setof contextual information that is mapped to the given transmissioncriterion; connecting, by the call routing server, the client device tothe remote telecommunications device using the phone number; andtransmitting, by the call context server, the set of contextualinformation to the remote telecommunications device or a computingdevice that is associated with the remote telecommunications devicewhile the call is being connected or in progress.
 28. The system ofclaim 27, wherein: receiving an indication that a click-to-call controlwas interacted with at a client device comprises receiving VoIP callinformation that specifies the phone number corresponding to theparticular digital component that was presented with the click-to-callcontrol; and transmitting the set of contextual information to theremote telecommunications device comprises embedding the set ofcontextual information in VoIP call setup data that is transmitted tothe remote telecommunications device.
 29. The system of claim 27,wherein transmitting the set of contextual information to the remotetelecommunications device comprises transmitting an audible message thataudibly conveys the set of contextual information when the remotetelecommunications device is activated to receive the call, but prior toenabling audio communications between a user of the client device and auser of the remote telecommunications device.
 30. The system of claim27, wherein: receiving a request to establish a call comprises receivinga request that specifies a search query that triggered presentation ofthe particular digital component that was visually presented with theclick-to-call control at the client device at a time of the interactionwith the click-to-call control; and transmitting the set of contextualinformation to the remote telecommunications device comprises generatingpacketized data that specifies a particular post call activity that ismapped to the given transmission criterion in the data store.